Upgrade materialize #781
Merged
Upgrade materialize #781
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After evaluating whether to upgrade to Material-UI for 2.4, I've decided to hold off until 3.0 for this. It seemed at first I could switch over the underlying components but I think it would introduce many bugs. Instead, I've opted to upgrade Materialize to v1.0. This pull request does that. All components should work the same and many of the bugs that were caused by the old version of Materialize should be resolved.
This PR also tries to take advantage of the react-materialize library, where possible. This has reduced the lines of code that UD needs to maintained.
This should resolve the following issues: